Designing Buildings - The Construction Wiki

Subjects

Edit this article

Last edited 23 Nov 2020

Information Delivery Manual (IDM)

An Information Delivery Manual (IDM) or Information Delivery Specification (IDS), can be used to identify discrete processes that are undertaken during the lifecycle of a built asset, and to detail the information required to carry them out.

The standards for IDM's are set out in:

The standards define an IDM as:

documentation which captures the business process and gives detailed specifications of the information that a user fulfilling a particular role would need to provide at a particular point within a project

They suggest that:

An IDM provides help in getting the full benefit from a BIM (building information modelling). If the required information is available in the BIM to support a construction process or use case, and the quality of information is satisfactory, then the process itself will be greatly improved. For this to happen, there needs to be a common understanding of the processes involved across the entire life cycle development of a built environment project, including the information that is required for and results from the execution of that process. This applies to any activity that results in an exchange of information and may not relate directly to a BIM, e.g. the process to arrive at a work plan or contractual agreement.

IDM's include:

Interaction maps: Representation of the roles and transactions relevant for a defined purpose.
Transaction maps: Representation of a set of messages that are exchanged between participating roles for a particular purpose.
Process maps: Representation of the relevant characteristics of a process associated with a defined business purpose.
Exchange requirements: A defined set of information units that needs to be exchanged to support a particular business requirement at a particular process phase.

For the users of BIM, it provides an easily-understandable description of:

Built asset lifecycle processes – where they fit and why they are relevant.
The requirements for information to be provided for the process to be carried out successfully.
Who the parties are who create, consume and benefit from the information.
Additional information that may be needed from the user.
How the information should be supported by software solutions.
The expected end results.